chore(fe): fix CVE-2025-64718 vulnerability - #2276
Merged
Merged
Conversation
paulushcgcj
approved these changes
Jun 16, 2026
Contributor
|
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Contributor
|
Contributor
|
Contributor
|
Contributor
|
Contributor
|
Contributor
|
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request addresses a security vulnerability in the js-yaml package by bumping the version via the project's dependency overrides.
Security Issue
CVE ID: [CVE-2025-64718]
Severity: Medium / High
Vulnerability Type: Prototype Pollution / Code Execution
Affected Package: js-yaml (transitive dependency via [Insert Transitive Parent Package, e.g., @nestjs/cli or stylelint])
Current Version: 4.1.1
Fixed Version: 4.2.0
Changes
Updated the js-yaml package version override from 4.1.1 to 4.2.0 in the application configurations to force the resolved dependency tree to utilize the patched version.
Files Changed
package.json — updated override configuration for the js-yaml package
package-lock.json — automatically updated via dependency resolution
Testing
Ran npm install to verify successful resolution without breaking peer dependency structures
Verified package-lock.json explicitly locks js-yaml at 4.2.0
Closing Issue
Closes #241
Thanks for the PR!
Deployments, as required, will be available below:
Any successful deployments (not always required) will be available here
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: